Can you share the steps to test this? (without using those test files)

Howdy @ShadowArcanist I completely understand why you want the exact step by step process on how to test it yourself instead of just relying on the test files.

I tested this on my own personal VPS running coolify just by plugging the file and testing.

Create your own git instance and test the bug.

If you know how to set up your own git instance ect and have been able to see the bug and the temporary fix then skip below.

• Use the one click deploy for Gitea to setup your own custom git. Follow the basic setup and create an account ect. launch it to git.example.com
• On Coolify, create a new ssh key and put it in your account ssh settings, not just an individual repo.

Run this command to fix ssh on gitea so that it listens on the correct port after running

docker exec -it <your_gitea_name> sh

sed -i 's/^SSH_PORT *= *.*/SSH_PORT = 22222/' /data/gitea/conf/app.ini

grep -E '^(SSH_PORT|SSH_LISTEN_PORT)' /data/gitea/conf/app.ini
exit

Make sure that your firewall allows ssh connection to gitea.

via ufw status

22222/tcp (v6) | ALLOW | Anywhere (v6)

Test out a custom git source via ssh://git@129.xxx.xxx.xx:22222/User/repo_name.git and make sure that it fails.

Test out a custom git source with the temporary fix viassh:///git@129.xxx.xxx.xx:22222/User/repo_name.git and make sure that it works.

If you are using cloudflare make sure that your DNS records are set to DNS only and not proxy.

Apply the patch.

Go into your coolify container

docker exec -u 0 -it coolify sh

rm bootstrap/helpers/shared.php
nano bootstrap/helpers/shared.php

and copy and paste the whole file in with my edits. Then,

exit

docker restart coolify

Test out custom git source again via ssh://git@129.xxx.xxx.xx:22222/User/repo_name.git and it should work!

Note

I personally had quite a few issues with recreating OP's original problem so I am 100% willing to answer any questions that you have about testing.

I have this patch running on my own VPS running coolify and its working on my machine (dangerous words ik.)

@coderabbitai do your thing!

@Iisyourdad I'll be back... with a full review! 🤖

Those are some excellent manual testing steps you laid out — self-hosted Gitea on your own VPS, custom SSH ports, and patching directly into the Coolify container. That's the way — real servers, real iron. None of that serverless nonsense where your SSH connection gets billed per millisecond. 🌮 (Sadly I can't enjoy your celebratory tacos, gluten intolerance and all.)

Let me do a thorough review of this PR right now!

No actionable comments were generated in the recent review. 🎉

Walkthrough

The pull request refactors the convertGitUrl() function to handle two distinct URL formats differently. For URLs containing ://, it now uses parse_url() to extract the port value directly without rewriting the repository URL. For SSH-style host:port/path format, it applies a named-group regex to extract port information and rewrites the repository accordingly. The changes include new feature and unit tests validating port extraction and preservation across SSH URLs with custom ports, including IPv6 hostname handling.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}